Method and system for performing remote treatment and monitoring

ABSTRACT

The disclosure relates to medical databases, remote monitoring, diagnosis and treatment systems and methods. In one particular embodiment, a system for remote monitoring, diagnosis, or treatment of eye conditions, disorders and diseases is provided. This method generally includes administering a stream of droplets to the eye of a subject from an ejector device, and storing data related to the administration in a memory of the ejector device. The data may then be monitored and analyzed.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 15/370,196, filed Dec. 6, 2016, which is a continuation of U.S. patent application Ser. No. 14/275,187, filed May 12, 2014, which a continuation of U.S. patent application Ser. No. 13/184,468, filed Jul. 15, 2011, now U.S. Pat. No. 8,733,935, which claims the benefit of the filing date of U.S. Provisional Application No. 61/400,864, filed Jul. 15, 2010, U.S. Provisional Application No. 61/401,850, filed Aug. 20, 2010, U.S. Provisional Application No. 61/401,920 filed Aug. 20, 2010, U.S. Provisional Application No. 61/401,918 filed Aug. 20, 2010, U.S. Provisional Application No. 61/401,848 filed Aug. 20, 2010, U.S. Provisional Application No. 61/401,849 filed Aug. 20, 2010, U.S. Provisional Application No. 61/462,576 filed Feb. 4, 2011, U.S. Provisional Application No. 61/462,791 filed Feb. 5, 2011, U.S. Provisional Application No. 61/463,280 filed Feb. 15, 2011, U.S. Provisional Application No. 61/516,462, filed Apr. 4, 2011, U.S. Provisional Application No. 61/516,496 filed Apr. 4, 2011, U.S. Provisional Application No. 61/516,495 filed Apr. 4, 2011, and U.S. Provisional Application No. 61/516,694, filed Apr. 6, 2011, the entire contents of each of which is specifically hereby incorporated by reference for all purposes. The present application is also related to U.S. Provisional Application No. 61/396,531 filed May 28, 2010, the entire contents of which is specifically hereby incorporated by reference for all purposes.

FIELD OF THE INVENTION

The disclosure relates to medical systems and methods. In particular, it relates to medical database, remote monitoring, diagnosis and treatment systems and methods.

BACKGROUND OF THE INVENTION

The monitoring, diagnosis and treatment of various conditions, disorders and diseases, such as eye conditions, disorders, diseases, etc., typically involve the regular physical intervention by a medical professional, requiring the subject to make an appointment and visit the doctor's or practitioner's offices. On the part of the subject, this involves travel time to the doctor and back, a waiting period and typically a face-to-face discussion with a nurse practitioner or doctor's assistant, followed by a discussion and examination by a doctor. Insofar as the subject is issued with a prescription, he or she then has to proceed to a pharmacy, wait for the prescription to be filled and finally proceed home. Thus, the treatment and monitoring of subjects is a highly time-consuming exercise.

From the practitioner's or provider's perspective, the number of subjects he or she can see is limited by the face-to-face time with each subject to discuss the subject's condition, arrange slip lamps and other scanning devices, examine the subject, update the subject's records and record the tests conducted for compliance and insurance purposes.

Even when subjects are scheduled for follow-up examinations pursuant to the use of certain medications, the practitioner merely has the opportunity to determine whether there is a change in the subject's condition, but still remains unable to verify whether or not the subject has regularly taken the medication and has done so in the correct dose. This equally applies to veterinary doctors. Thus, notwithstanding the time-consuming nature of in-person examinations, the decisions that can be drawn from the analysis remain largely speculative and inconclusive.

Thus, comparisons to prior results of a particular subject, and comparisons to other subjects treated with the same drugs, can only act as an approximation due to the many unknowns. The inaccuracies in the results may be ascribed to both human error and the limitations of current dispensing devices. An additional problem is that subjects may forget to dose or double-dose or cross-dose with other medications. Even when subjects administer medication correctly (or have the medication correctly administered), current technology does not provide a satisfactory way of controlling the amount of medication that is dispensed, nor does it provide a way of ensuring that the medication that is dispensed actually reaches the eye and remains in the eye.

Current approaches fail to provide an accurate way of monitoring the administration of medication and dosages. The present disclosure addresses such shortcomings in addition to others.

SUMMARY OF THE INVENTION

In one aspect, according to the disclosure, there is provided a system for monitoring a subject, e.g., for compliance with a dosing regimen, for analysis of treatment, for diagnosis, etc., the system generally comprising at least one ejector device configured for administering a stream of droplets to the eye of a subject in need thereof, wherein the ejector device comprises a memory for storing subject-specific data and a communication interface for communicating said stored data. In certain embodiments, the system further comprises a docking station configured to interface with the ejector device and to communicate with said ejector device. In certain embodiments, the system comprises at least one database or server in communication with said ejector device. In some embodiments, the ejector device is in communication with said database or server via the docking station.

In another embodiment, methods are provided which generally include: (1) administering a stream of droplets to the eye of a subject in need thereof using an ejector device as described herein; and (2) storing data in a memory of the device, the data relating to, e.g., dosing regimen information, image information, etc. In certain embodiments, the method may further include (3) communicating the stored data from the ejector device, e.g., to a docking station, database or server, and/or user terminal. The communicated data may then be stored in memory in the docking station, the database or server, or in a memory on the user terminal. In yet other embodiments, the data communicated from the device (e.g., from the docking station, database or server, or via the user terminal) may be reviewed and analyzed. Based on such review and analysis, in one embodiment, the method may include adjusting dosages and medicaments as needed.

In another embodiment, the ejector device may include an image capturing device, and the method may include communicating image information (e.g., ocular image information). The method may include reviewing and analyzing the image information to diagnose the subject, e.g., by comparing image information to previous images obtained from the same subject or to images obtained from other subjects.

In another embodiment, approved providers may sign onto the system and through a user interface set parameters, with, for example, a look-up table, that the device will read to adjust dosage amounts, dosage timing and other reminders.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a front view of an ejector device in an embodiment of the disclosure;

FIG. 2 shows a docking station of an embodiment of the disclosure;

FIG. 3 shows a system in an embodiment of the disclosure; and

FIGS. 4-8 show exemplary user interface depictions in accordance with embodiments of the disclosure.

DETAILED DESCRIPTION OF THE INVENTION

A major concern in medical treatment, e.g., in the treatment of glaucoma, is the failure by subjects to regularly take their medication. Subjects either forget to take the medication or fail to take the correct dosage, e.g., to get the correct number of drops into the eye due to the difficulty of using a conventional eye dropper. In part, to address issues encountered with the use of conventional eye droppers, ejector devices, such as those described in U.S. Application Attorney Docket No. 24591.003-US03, filed concurrently herewith, entitled Drop-Generating Device, the contents of which are herein incorporated by reference in their entirety, may be used in connection with the present disclosure.

In another aspect, the disclosure provides a device for administering a fluid to the eye, such as an eye medication (e.g., anti-histamine) eye solution, eye lubricant or eye wetting agent, pupil dilator, fluorescein, anesthetic, suspended solid, etc., in a stream of droplets to the eye. However, the disclosure is not limited to use in connection with administration to the eye. For instance, other topical, inhaled, parenteral, oral, etc., delivery routes are envisioned as within the scope of the present disclosure. In one embodiment, the disclosure may be implemented using a device or applicator in the form of a thermal ejector, ultrasonic ejector, or piezo ejector generating ejected fluid droplets.

In one embodiment, an ejector device is provided with a memory for storing data such as subject-related information, e.g., dosing regimen information, etc. Any suitable memory or data storage media may be used, in certain embodiments, such memory may be in the form of a Flash memory drive with a universal serial bus (USB) port, which allows communication with a processing device, computer or user terminal. The Flash memory device (FMD) in one embodiment is preprogrammed to include its own user interface, which may be implemented as a graphical user interface (GUI). The FMD may include content data, e.g., subject information data, and applications. The GUI may include links for accessing at least some of the content data remotely. The GUI may also include Internet links, typically in the form of Web links. The FMD may be operable to launch a browser when an Internet link is clicked. The browser may be a browser that is installed on the processing device, computer or user terminal with which the FMD is in communication. Instead, a browser may be locally stored on the FMD or may be downloaded from a server. The FMD may be implemented to launch the browser automatically when the FMD is in communication with a processing device, computer, or user terminal, if such device, etc., is detected to have Internet access, or the browser may be launched manually by the user, e.g., by clicking an Internet link. In certain embodiments, the processing device, computer, user terminal, etc., may include a desktop computer, laptop, Personal Digital Assistant (PDA), smartphone, etc.

In certain embodiments, the ejector device may include an a controller or processor for controlling the dosing of a medicament (i.e., dosing regimen). In order to ensure proper use by the subject, the controller may control dispensing of one or more medications to correspond to defined dosing times and dosing amounts and may monitor the amount of fluid dispensed during each dosing time to ensure delivery of the full dose. Such information may then be stored in the memory of the ejector device. The controller may also be programmed with dosage information (e.g., by a medical professional) and may be updated remotely to include new dosing information or new medication information, if needed.

More specifically, in one embodiment, with reference to FIG. 1, the present disclosure, in part, relates to an ejector device 100 having an alarm, which in this embodiment comprises an audible alarm, e.g., in the form of a speaker 110, a visual alarm, e.g., in the form of a LED 112 mounted on the device housing, a tactile alarm, e.g., a vibration mechanism (not shown). The subject is notified when a dose needs to be taken, or a missed dose is detected. In an embodiment, a controller, processor or other programmable means (not shown) may be programmed with dosage and treatment regimen information to send a signal to the speaker 110 and/or LED 112 at the time a dose needs to be taken. In another embodiment, the device 100 alarm may be remotely initiated, e.g., by cell-phone, remote calendar, etc. Device 100 also may include a targeting mechanism 130 to aid in aligning dosing of the device. In certain aspects, targeting mechanism may be a low-intensity light beam, e.g., a low-intensity or filtered light emitting diode (LED) which emits a beam when, e.g., the ejector device is activated. In certain embodiments, the light beam may be configured to shine into the user's eye when the ejector device is correctly aligned with the eye. In other embodiments, ejector device 100 may include one or more illuminating devices, e.g., LEDs or other illuminating devices in addition to the targeting device 130, capable at illuminating at varying desired wavelengths. In certain instances, such illuminating devices may be useful in treatment or diagnosis of subjects alone or in connection with administration of agents (e.g., pupil-dilating agents, dyes, therapeutic agents, etc.). Alternatively, illuminating devices may be used in connection with image capture device 150 (below) to aid in obtaining quality image capture.

By way of example, the ejector device may include one more illuminating devices of varying wavelengths such as a red light, blue light, green light, white light, and/or IR light, which may be implemented by making use of LEDs. Monochromatic light sources may be used for monochromatic fundus imaging, preferably below 540 nm wavelength. This involves the imaging of the ocular fundus with the use of colored or monochromatic illumination to enhance the visual contrast of anatomical details of the fundus.

The device may also include an image capture device for obtaining images of the eye or structures of the eye (e.g., retina, pupil, cornea, etc.). By way of example, in the embodiment of FIG. 1, the image capturing device may comprise a camera in the form of a charge coupled device (CCD) 150, retinal scanner or other camera to capture images of the eye. In one embodiment, the images may include images showing the effect of pressure on the cornea, for purposes of diagnosing potential glaucoma, or may include images taken using different wavelength illumination to obtain information about the health of the eye, etc. The images may be stored in the memory in the device, and subsequently downloaded to the docking station and/or a remote memory or database, as discussed herein.

In some embodiments, the image capture device may be utilized to detect the presence of an eye and to ensure that the eye is open and/or that correct alignment of the eye is detected. The image capture device may provide information to the controller or processor, which, in one embodiment, provides a signal to initiate activation of the ejector device when opening of the eye and/or correct alignment of the eye, is detected. Alternatively, a reflective surface mounted on or incorporated within the ejector device, or an infra-red (IR) transmitter (e.g., IR LED) and photo detector may be mounted on the front surface of the ejector device (not shown). In certain aspects, the IR transmitter may transmit an infra-red beam or pulse, which is received by an IR photo detector when the ejector device is correctly aligned with the eye, and the IR beam or pulse is reflected off the eye and the beam or pulse is reflected to the IR photo detector.

In one embodiment, the ejector device described herein provides a user, e.g., a medical professional and/or subject, information regarding a subject's compliance with a particular dosage regimen. In one embodiment, the device includes a memory and controller, processor, etc., further includes software, programmable executable code, etc., to store information regarding dosing, e.g., the dates and times that the device is used and the volumes ejected. This information may be stored on a memory chip or other suitable memory storage media for subsequent retrieval. In certain implementations, the information may be retrieved via an input/output (I/O) port or wireless interface, such as a Universal Serial Bus (USB), an Infrared Data Association IrDA interface, a BLUETOOTH® wireless transceiver, etc.

It will be appreciated that the disclosure has been described with respect to different embodiments of the ejector device; however, the invention is not limited to the specific embodiments, but can be implemented in different ways without departing from the scope of the disclosure.

In another embodiment, the ejector device may communicate with a docking station. For example, with reference to FIG. 2, the ejector device may communicate with docking station 200. In certain embodiments, docking station 200 may generally include a memory (volatile, non-volatile, or combinations thereof), an I/O port or wireless interface for communicating with a public or private network, and a communication interface for communication with the ejector device. In certain embodiments, there may be a single communication interface for communicating with networks and the ejector device, or the docking station may include multiple communication interfaces. Docking station 200 may allow the data stored in memory of the ejector device to be downloaded or otherwise communicated to the docking station via, e.g., engagement of a docking port of the device with the communication interface of the docking station. Alternatively, input/output port or wireless interface of the ejector device may interface and/or communicate with the communication interface of the docking station. Such data may be downloaded or otherwise communicated on-demand (i.e., upon user docking), or at predetermined communication intervals (i.e., at predetermined times such that the ejector device attempts communication with the docking station, e.g., via a wireless communication network).

Docking station 200 may also include charging contacts (not shown) to engage with receiving contacts on the device to charge re-chargeable batteries in the device, if desired. In certain embodiments, the data may be stored in memory in the docking station 200. The docking station 200 may also be in communication, either wired or wirelessly, with a private or public network, e.g., via the I/O port or wireless interface of the docking station. In certain embodiments, data stored in memory of the device may be transferred or communicated, via the docking station and/or the I/O port of the device, and via a network to a remote server for storage in a remote memory or database.

In accordance with certain embodiments of the invention, the docking station may include a processor or controller, which in certain embodiments, may comprise software or computer executable code that enable functionality/diagnostics checks of the operation of the ejector device when the ejector device is in communication with the docking station, or at predetermined time intervals, etc.

In other embodiments (not shown), the docking station may include tactile, visual, and/or audible alarms. Such alarms may provide dosing reminders to a user, both on an automated treatment and a corrective treatment basis (e.g., based automated dosing regimen reminders and reminders if doses are missed). As explained herein, a medical professional may communicate with the ejector device through the communication interface of the docking station, or may communicate directly with the ejector device (e.g., to modify dosing regimen).

In another embodiment, a system including at least one ejector device and an optional docking station is provided. The systems of the present disclosure may also include the ability to communicate, e.g., via a communication network to a database or server, or user terminal. In one embodiment, a system for monitoring subject compliance with a dosing regimen is provided. Such systems can further be utilized to monitor and analyze treatment and, e.g., adjust dosing regimens accordingly, as discussed herein. Further, such systems may be used to diagnosis subjects based on data collected. The system generally comprising an ejector device configured for administering a stream of droplets to the eye of a subject in need thereof, wherein the ejector device comprises a memory for storing subject specific data and a communication interface for communicating the stored data. In some embodiments, the ejector device comprises an image capture device. In certain embodiments, the system further comprises a docking station configured to interface with the ejector device and to communicate with the ejector device.

In certain embodiments, the system comprises one or more databases or servers in communication with the ejector device(s). The databases or servers are configured to store data received from the ejector device, the docking station, or combinations thereof. In some embodiments, the ejector device is in communication with the database or server via the docking station. In certain embodiments, the database or server may be a compliance database or an adherence database. The database or server may store one or more medical records for a user of the ejector device, and the record may include data collected by the ejector device. In certain embodiments, the database may be integrated with an Electronic Medical Record (EMR) system, as the term is understood by those of skill in the art.

By way of example, FIG. 3 illustrates a system 300 including an ejector device 301 interfaced (e.g., physically interfaced, in wired or wireless communication, etc.) with a docking station 302, which is networked (wired or wirelessly, including via a public or private network such as the Internet as depicted by the communication network cloud 304) for communicating data for storage in a memory of a database or a server 306. A user or medical professional, e.g., physician, or other expert located remotely at user terminal 310 can then access some or all of the data on the server or database 306. In certain embodiments, as understood by those in the art, the database or server 306 may be secured, e.g., by a user identification code or other security measure, to ensure that only authorized users have access to the data. Further, in certain embodiments, the database or server may be secured so as to only give access to certain portions of the data to certain users, etc. (e.g., based on subject privacy concerns). In certain aspects, the device 300, database or server 306, terminal 310, etc., may be configured to allow two-way communication, e.g., via communication network 304, such that a user may upload data to ejector device 300. By way of example, the data may include subject-specific information, such as compliance information, dosing regimen information, e.g., two drops twice a day of drug A in both eyes at defined times of the day, 1 drop in each eye of drug B, etc.

Although the example of FIG. 3 shows the database or server 306 as being separate (and at a separate location) from the ejector device 301, the base station 302, and the user terminal 310 (not shown) this is not necessarily the case. However, the database or server 306 may be co-located with the user terminal 310, or may be configured to interact with multiple devices similar to the ejector device 301, such that the database 306 may store information for multiple devices used by a particular user and/or information about multiple patients, each of whom use one or more devices such as the ejector device 301. Further, in some embodiments, database or server 306 may be distributed across multiple databases and servers, or the information may be distributed across database or server 306, and one or more of ejection device 301, base station 302, or user terminal 310.

In certain embodiments, a user may access, review and/or analyze data from an ejector device, database, server, etc., via a user interface such as a graphical user interface (GUI) on a computer in communication with the device, database, server, etc. Exemplary GUI embodiments are illustrated in FIGS. 4-8. FIG. 4 shows an overview page with various subject identifiers 400 (e.g., names and dates of birth). Column 402 defines a right and left eye treatment for each subject. Columns 404 provide individual columns for the various treatment weeks, each eye for each subject being, e.g., coded to indicated full compliance by the subject with dosage requirements (green), partial compliance (orange) or no compliance (red). In another embodiment (not shown) coding may be used to indicate different drug types.

FIG. 5 shows an individual subject record. The various columns correspond to information by week, and the rows correspond to each day. The upper portion provides subject details 500 and treatment regimen details 502. As shown in FIG. 6, clicking on any of the cells in the subject detail array allows additional information to be viewed, insofar as there is additional information, such as images captured of the eye, date of the image and subject details, etc., thereby allowing a visual record over time. This allows a medical professional to remotely monitor not only subject compliance with dosing regimen, but also to remotely monitor visual diagnostic information and interact with the subject as needed.

FIG. 7 illustrates yet another embodiment including subject compliance detail information. FIG. 7 shows compliance data detail, e.g., for each medicament to be administered per a dosing regimen in section 700, and a graphical display 702 showing level of compliance for each eye and a selected medicament. As shown in FIG. 8, clicking on any of the cells in the subject detail array allows additional information to be viewed, insofar as there is additional information, such as images captured of the eye, date of the image and subject details, etc., thereby allowing a visual record over time. Again, this allows a medical professional to remotely monitor not only subject compliance with dosing regimen, but also to remotely monitor visual diagnostic information and interact with the subject as needed.

In certain embodiments, the systems and ejector devices described herein allow for the remote monitoring of one or more subjects, and may allow a medical professional to remotely diagnosis, treat and adjust treatment as needed. By way of example, the systems and ejector devices may allow for the capturing, storage, and communication of data related to dosing regimen compliance information, image information, etc., which information may be reviewed and analyzed. If desired, the information may be compared to earlier information related to the same subject, information from multiple subjects (i.e., information from multiple subjects may be stored in a central database and compared based on demographics information about the users, dosage and type of medicament, etc.).

In yet another embodiment, methods are provided which generally include: (1) administering a stream of droplets to the eye of a subject in need thereof using an ejector device, such as those described herein; and (2) storing data in a memory of the device, the data relating to, e.g., dosing regimen information, image information, etc. In certain embodiments, the method may further including (3) communicating the stored data from the ejector device, e.g., to a docking station, database or server, and/or user terminal. The communicated data may then be stored in memory in the docking station, the database or server, or in a memory on the user terminal. In yet other embodiments, the data communicated from the device (e.g., from the docking station, database or server, or via the user terminal) may be reviewed and analyzed. Based on such review and analysis, in one embodiment, the method may include adjusting dosages and medicaments as needed. In one example, if desired results are not observed in the data, the dosage regimen may be increased (dosage amounts, number of dosages, etc.). Alternatively, if results indicate such, the dosage regimen may be decreased. In yet another embodiment, the ejector device may include two or more medicaments, wherein a first medicament is used and monitored for a first period of time and if the desired results are not achieved, administration is changing to a second or third medicament.

In another embodiment, the ejector device may include an image capturing device, and the method may include communicating image information (e.g., ocular image information). The method may include reviewing and analyzing the image information to diagnose the subject, e.g., by comparing image information to previous images obtained from the same subject or to images obtained from other subjects. In some embodiments, image information may be obtained independently of administration of a stream of droplets, prior to such administration, concurrently with such administration, subsequent to such administration, or a combination thereof.

In one embodiment, a method for monitoring ophthalmic subjects is provided. The method generally includes administering a stream of droplets to the eye of a subject in need thereof using an ejector device described herein (e.g., a device including a memory for storing subject-specific data and a communication interface for communicating said stored data); and storing said data in the memory of the device. The method can further include analyzing the communicated data from the ejector device and adjusting administration of the stream of droplets to the eye of the subject as needed, based on said analysis.

In other embodiments, the method includes receiving subject-specific data from an ejector device, the ejector device configured for administering a stream of droplets to the eye of a subject in need thereof; storing the data in at least one database; analyzing the stored data; and adjusting administration of the stream of droplets to the eye of the subject as needed, based on said analysis.

In yet other embodiments, the ejector device may further include an image capturing device for capturing images of the eye of the subject. The method may further include capturing images of the subject's eye; and storing the images in the memory of the device.

In one embodiment, the subject is being treated for glaucoma, and the stream of droplets administered to the eye comprises a medicament for the treatment of glaucoma. In certain embodiments, the subject-specific data includes dosing regimen information related to the treatment of glaucoma, information related to the subject's compliance with the dosing regimen, etc.

In yet another embodiment, a method for diagnosis of ophthalmic subjects is provided. The method generally includes: capturing images of a subject's eye using an ejector device; storing the images in the memory of the device; and analyzing the images to thereby diagnose the subject based, at least in part, on analysis of said images.

In another embodiment, methods for the diagnosis for glaucoma are provided, which typically include the exertion of pressure on the cornea, e.g., Goldmann applanation tonometry, and which involves the application of Fluress® (comprising a fluorescent agent, an anesthetic, a preservative, and a wetting agent and stabilizing agent), followed by the applanation using a 3.06 mm² device. For intraocular pressures of 20 mmHg or less, the accuracy of the measurement should be within +0.5 and −0.5 mmHg. The present disclosure provides a method for diagnosis of glaucoma, generally comprising applying pressure to avoid the use of an applanation device. By ejecting a selectable number of droplets of liquid, e.g., saline solution onto the eyeball from a defined distance, the pressure exerted on the cornea and intraocular pressure can be determined based on the deformation, which can be captured by the image capture device. In one embodiment, a reservoir includes a saline compartment, which is manually selectable by means of a selector switch mounted on the device, or the saline compartment is selected by having the physician upload medication type and dose information that selects a certain number of droplets of saline solution to define a certain pressure. Feedback information captured by the image capture device may be uploaded to the database or server, to allow the doctor to diagnose the condition and either adjust the pressure of a second ejection cycle or schedule a follow-up appointment for the subject.

In certain embodiments, the systems and methods of the disclosure may be used to monitor the treatment of chronic problems such as glaucoma. Stored data may be reviewed and analyzed, e.g., to evaluate patient compliance, to evaluate efficacy of dosing regimen, to determine necessary changes to dosing regimen, and to implement changes as needed.

The systems and methods of the present disclosure may also be used for situational applications, such as the delivery of medication after cataract or other ophthalmic surgery to facilitate self-administration of prescribed medications at defined times and defined dosages. Other embodiments include, but are not limited to: conjunctivitis treatments; allergy treatments; saline application for those who wear contact lenses; sore, irritated, red-eye treatments; application of dilation medications; decongestants that shrink or constrict blood vessels and cause the eye to whiten; corticosteroids such as Prednisolone®, Dexamethasone®, Hydrocortisone®, Fluoromethalone®, Medrysone®, Rimexolone®, etc.

In the case of medicaments where the exact or low dosage is of importance, the systems and methods of the disclosure may be of particular use. For instance, some of the medications that can be dispensed using the device of the invention include, but are not limited to: glaucoma medications such as ocular hypotensive agents for glaucoma, including but not limited to the prostaglandin analogues, such as Xalatan® (latanoprost) by Pfizer, Lumigan® (bimatroprost) by Allergan, Travatan® (travoprost) by Alcon may be applied; alpha agonists such as Alphagan® P (brimonidine) by Allergan, and Combigan® (brimonidine/timolol) by Allergan, and beta blockers such as Timolol®; carbonic anhydrase inhibitors such as Trusopt® (dorzolamide) by Merck, Cosopt® (dorzolamide/timolol) by Merck, and Azopt® (brinzolamide) by Alcon; antibiotics such as “4^(th) Generation” Fluoroquinolones for perioperative infection prophylaxis); Zymar® (gatifloxacin) by Allergan; Vigamox® (moxifloxacin) by Alcon; anti-inflammatory such as steroids like Prednisolone® acetate 1%—generic, Pred Forte® by Allergan, Omnipred® by Alcon, and Difluprednate (Durezol®) by Alcon; non-steroidal such as Acuvail® (ketorolac) by Allergan, Xibrom® (bromfenac) by Ista; Nevanac® (nepafenac) by Alcon, and Ketorolac®; combination antibiotic/steroid preparations frequently used for post operative subjects, including Tobradex® (tobramycin/dexametasone solution, Alcon); etc.

As discussed herein, medicaments are generally discussed in the context of ophthalmic medication including a therapeutically active agent. However, medicaments are not so limited and include all ophthalmic liquids, such as an eye medication (e.g., anti-histamine) eye solution, eye lubricant or eye wetting agent, pupil dilator, fluorescein, anesthetic, etc.

In another embodiment, providers can get onto the system and through a user interface, set parameters of a database so that the device will read to adjust dosage amounts, dosage timing and other reminders. Additionally, with patient-identifying information removed, such as for example in accordance with HIPAA privacy policies, this database becomes a significant asset for example to pharmaceutical companies for data mining and insurance companies for underwriting. Once patient-identifying data is scrubbed, a host of reports can be generated for interested parties. Indeed, the capabilities of this database, in combination with the device, promise a new standard of care in the industry, providing a comprehensive solution to improve overall compliance/adherence, minimize office visits, reduce probability of blindness due to glaucoma and improve quality of life.

The present disclosure has been disclosed with reference to specific embodiments. It will, however, be appreciated that the invention is not so limited. 

1. A system for treating ophthalmic subjects, comprising at least one ejector device configured for administering a stream of droplets to an eye of a subject in need thereof, wherein said ejector device comprises: a memory for storing subject-specific data, a communication interface for communicating said stored data, an image capture device to capture images of the eye, the subject-specific data including image information captured by said image capture device, the images of the eye of the subject sufficient to obtain information about the diagnosis or health of the eye, a reservoir disposed within a housing of the ejector device for receiving a volume of ophthalmic fluid, and an ejector mechanism coupled to the reservoir, the ejector mechanism configured to eject the stream of droplets; and at least one database or server in communication with said ejector device.
 2. A system of claim 1, further comprising at least one docking station configured to interface with said at least one ejector device and to communicate with said ejector device(s).
 3. A system of claim 2, wherein said ejector device(s) communicate with said docking station(s) via a wired or wireless communication interface.
 4. A system of claim 2, wherein said ejector device comprises an I/O port configured to interface with said docking station.
 5. A system of claim 2, wherein said at least one ejector device is in communication with said at least one database or server via said docking station.
 6. (canceled)
 7. A system of claim 1, further comprising a user terminal.
 8. A system of claim 8, wherein said user terminal is selected from the group consisting of a computer, a smartphone, and a PDA.
 9. A system of claim 8, wherein said system is configured for two-way communication between said at least one ejector device and said user terminal.
 10. A system of claim 1, wherein said at least one ejector device includes a piezo electric ejector or thermal ejector.
 11. A method for monitoring ophthalmic subjects, the method comprising: administering a stream of droplets to an eye of a subject in need thereof using an ejector device, said ejector device comprising: a memory for storing subject-specific data, a communication interface for communicating said stored data, an ejector mechanism coupled to a reservoir for receiving a volume of ophthalmic fluid, a piezo electric actuator configured to oscillate the ejector mechanism at a frequency to eject the stream of droplets upon actuation, and an image capture device to capture images of the eye, the subject-specific data including image information captured by said image capture device, the images of the eye of the subject sufficient to obtain information about the diagnosis or health of the eye; and storing said data in the memory of said device.
 12. (canceled)
 13. A method of claim 11, further comprising communicating said stored data from said ejector device to a docking station, database or server, and/or user terminal.
 14. A method of claim 13, further comprising analyzing the communicated data from said ejector device and adjusting administration of said stream of droplets to the eye of said subject as needed, based on said analysis.
 15. A method of claim 11, wherein said subject is being treated for glaucoma, and said stream of droplets administered to the eye comprises a medicament for the treatment of glaucoma.
 16. A method of claim 15, wherein said subject-specific data includes dosing regimen information related to the treatment of glaucoma.
 17. A method of claim 16, wherein said subject-specific data includes information related to said subject's compliance with the dosing regimen.
 18. A method for monitoring ophthalmic subjects, the method comprising: receiving subject-specific data from an ejector device, said ejector device configured for administering a stream of droplets to the eye of a subject in need thereof, the ejector device comprising: an image capture device configured to capture images of the eye, the subject-specific data including image information captured by said image capture device, the images of the eye of the subject sufficient to obtain information about the diagnosis or health of the eye; storing said subject-specific data in at least one database; analyzing the stored subject-specific data; and adjusting administration of said stream of droplets to the eye of said subject as needed, based on said analysis.
 19. A method of claim 18, wherein analyzing the stored subject-specific data comprises analyzing the images or image information to thereby diagnose said subject based, at least in part, on analysis of said images or image information, wherein adjusting administration of said stream is based on the analysis of said images or image information.
 20. A method of claim 18, wherein said subject is being treated for glaucoma, and said stream of droplets administered to the eye comprises a medicament for the treatment of glaucoma.
 21. A method of claim 15, wherein said subject-specific data includes dosing regimen information related to the treatment of glaucoma.
 22. A method of claim 16, wherein said subject-specific data includes information related to said subject's compliance with said dosing regimen.
 23. (canceled) 